Summary

What changed?

• Introduced more specific logging categories for gRPC worker logs: Microsoft.DurableTask.Worker.Grpc (previously Microsoft.DurableTask)
• Added DualCategoryLogger class that emits logs to both new specific categories and legacy Microsoft.DurableTask when UseLegacyCategories is true
• Added DurableTaskWorkerOptions.Logging.UseLegacyCategories configuration option (default: true) for backward compatibility
• Updated IntegrationTestBase.GetLogs() to use the specific category to avoid duplicate matching when dual-category logging is enabled
• Added comprehensive unit tests for the dual-category logging feature
• Improved exception handling in CompositeDisposable.Dispose() to ensure both disposables are cleaned up even if one throws
• Improved integration tests to verify the actual worker logger type using reflection with extracted helper methods

Why is this change needed?

The current logger category assignments are overly broad. Logs related to work item processing and gRPC are under the generic Microsoft.DurableTask category, making them hard to filter. This change introduces more specific categories while maintaining backward compatibility through dual-emission logging.

Issues / work items

• Fixes Make logging categories more specific #407 (Make logging categories more specific)
• Related Add specific logging categories for Worker.Grpc and orchestration logs with backward-compatible opt-in #551 (test failure from dual-category logging changes)

Project checklist

• Release notes are not required for the next release
• Backport is not required
• All required tests have been added/updated (unit tests, E2E tests)
• Breaking change?
  • Setting UseLegacyCategories = false stops emitting to Microsoft.DurableTask category
  • Log filters expecting this category will need updates
  • Default behavior (UseLegacyCategories = true) is non-breaking

AI-assisted code disclosure (required)

Was an AI tool used? (select one)

• No
• Yes, AI helped write parts of this PR (e.g., GitHub Copilot)
• Yes, an AI agent generated most of this PR

If AI was used:

• Tool(s): GitHub Copilot Agent
• AI-assisted areas/files:
  • src/Worker/Core/DurableTaskWorkerOptions.cs (LoggingOptions class)
  • src/Worker/Grpc/DualCategoryLogger.cs (new file)
  • src/Worker/Grpc/GrpcDurableTaskWorker.cs (CreateLogger method)
  • test/Grpc.IntegrationTests/IntegrationTestBase.cs
  • test/Worker/Grpc.Tests/LoggingCategoryTests.cs (new file)
  • test/Worker/Grpc.Tests/RunBackgroundTaskLoggingTests.cs
• What you changed after AI output: Reviewed and verified the implementation, fixed exception handling in CompositeDisposable.Dispose, improved tests with reflection and helper methods, consolidated documentation

AI verification (required if AI was used):

• I understand the code and can explain it
• I verified referenced APIs/types exist and are correct
• I reviewed edge cases/failure paths (timeouts, retries, cancellation, exceptions)
• I reviewed concurrency/async behavior
• I checked for unintended breaking or behavior changes

Testing

Automated tests

• Result: Passed (117 integration tests, 43 Worker.Grpc.Tests including 8 logging category tests)

Manual validation (only if runtime/behavior changed)

• N/A (logging infrastructure change, behavior validated through automated tests)

Notes for reviewers

• Migration Path:

services.AddDurableTaskWorker(options =>
{
    // Step 1: Update your log filters to use new categories
    // Step 2: Test with both categories emitting (default)
    // Step 3: Disable legacy when ready
    options.Logging.UseLegacyCategories = false;
});

• The DualCategoryLogger ensures backward compatibility by emitting to both the new specific category and the legacy Microsoft.DurableTask category when UseLegacyCategories is true (default)
• Test infrastructure was updated to use the specific new category to avoid duplicate log matching
• Integration tests use reflection with helper methods (CreateWorkerWithLoggingOptions and GetWorkerLogger) to verify the actual worker logger type

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.